Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
||
| <Callout type="info"> | ||
| Bearer tokens are fetched automatically for each API request using your client credentials. | ||
| You don't need to manage token expiration or refresh - it's handled for you! |
There was a problem hiding this comment.
Google.Exclamation: Removed exclamation point from documentation text
| You don't need to manage token expiration or refresh - it's handled for you! | |
| You don't need to manage token expiration or refresh - it's handled for you. |
| **Parameters** | ||
|
|
||
| - **restaurant_external_id** (`string`, required): The Toast platform GUID for the restaurant. | ||
| - **business_date** (`string`, required): The business date in YYYYMMDD format (e.g., 20240115). |
There was a problem hiding this comment.
Google.Latin: Replaced 'e.g.' with 'for example'
| - **business_date** (`string`, required): The business date in YYYYMMDD format (e.g., 20240115). | |
| - **business_date** (`string`, required): The business date in YYYYMMDD format (for example, 20240115). |
| **Parameters** | ||
|
|
||
| - **restaurant_external_id** (`string`, required): The Toast platform GUID for the restaurant. | ||
| - **business_date** (`string`, required): The business date in YYYYMMDD format (e.g., 20240115). |
There was a problem hiding this comment.
Google.Latin: Replaced 'e.g.' with 'for example'
| - **business_date** (`string`, required): The business date in YYYYMMDD format (e.g., 20240115). | |
| - **business_date** (`string`, required): The business date in YYYYMMDD format (for example, 20240115). |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| "toast-api": { | ||
| title: "Toast POS API", | ||
| }, | ||
| }; |
There was a problem hiding this comment.
Missing default theme configuration in hospitality meta
Medium Severity
The hospitality/_meta.tsx file is missing the "*" default theme configuration that all other integration category meta files include. Every other category (databases, payments, entertainment, sales, customer-support, etc.) has a "*": { theme: { breadcrumb: true, toc: true, copyPage: true } } entry. Without this, the Toast API page will render without breadcrumb navigation, table of contents, and copy page functionality, making it inconsistent with all other integration pages.
|
@avoguru the Toast starter toolkit docs look ready to merge. Want to go ahead and ship it? |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
| - **Cash Management**: View cash drawer entries and bank deposits | ||
| - **Restaurants**: Access restaurant configurations and management groups | ||
|
|
||
| This server is designed to streamline restaurant management and enable AI-powered automation of hospitality operations. |
There was a problem hiding this comment.
Google.Passive: Changed passive voice 'is designed to' to active voice
| This server is designed to streamline restaurant management and enable AI-powered automation of hospitality operations. | |
| This server streamlines restaurant management and enables AI-powered automation of hospitality operations. |
| | `loyalty:read` | Not supported | See note below | | ||
|
|
||
| <Callout type="warning"> | ||
| **Loyalty API Limitation**: The `loyalty:read` scope is not currently supported. The Toast Loyalty Integration API is a **webhook-based** system where Toast sends loyalty transaction events to your endpoint - it is not a read API that can be called to retrieve loyalty data. If you need loyalty functionality, contact Toast directly about their loyalty data access options. |
There was a problem hiding this comment.
Arcade.WordList: Changed 'functionality' to 'feature' as specified in the word list rule
| **Loyalty API Limitation**: The `loyalty:read` scope is not currently supported. The Toast Loyalty Integration API is a **webhook-based** system where Toast sends loyalty transaction events to your endpoint - it is not a read API that can be called to retrieve loyalty data. If you need loyalty functionality, contact Toast directly about their loyalty data access options. | |
| **Loyalty API Limitation**: The `loyalty:read` scope is not currently supported. The Toast Loyalty Integration API is a **webhook-based** system where Toast sends loyalty transaction events to your endpoint - it is not a read API that can retrieve loyalty data. If you need loyalty feature, contact Toast directly about their loyalty data access options. |
Note
Introduces hospitality docs and Toast POS API tooling documentation.
hospitalitycategory toapp/en/resources/integrations/_meta.tsx("Retail & Hospitality")app/en/resources/integrations/hospitality/toast-api/page.mdxwith comprehensiveToastApidocs: auth (client credentials), scope coverage, and tool references (orders, menus, kitchen, labor, inventory, cash mgmt, restaurant info)app/en/resources/integrations/hospitality/_meta.tsxto registerToast POS APIpublic/llms.txtto include the newToastApidocs linkWritten by Cursor Bugbot for commit 911b05f. This will update automatically on new commits. Configure here.